fix: confirm cost before enabling paid mfa addons#4076
Merged
sweatybridge merged 1 commit intodevelopfrom Sep 9, 2025
Merged
Conversation
113d941 to
c0458d2
Compare
avallete
approved these changes
Aug 25, 2025
Member
avallete
left a comment
There was a problem hiding this comment.
Code looks good.
FMI how does it work for branches ? Enabling those for branches does also incurs extra cost on top of the project ? Is it included ?
I'm wondering if a user might mistakingly activate the options on every branches just because it use a single config.toml between branching/prod 🤔
Izzaddin97
approved these changes
Sep 6, 2025
Contributor
Author
Yup it will incur extra costs if enabled on branches. Probably would recommend disabling in base config and enable only in remotes block. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Bug fix
What is the new behavior?
Avoids bill shock when user accidentally enables paid addons from config push.
Additional context